Fix diff suppress function ignoring additive_vpc_scope_dns_domain in Autopilot clusters #12567
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
self-appointed successor to #11744
GKE Autopilot allows setting additive VPC scope domain on creation only. However, current implementation of the diff suppress function for Autopilot clusters removes any values in dns_config of Autopilot clusters, all the time.
This change permits setting additive VPC scope domain.
Remaining action items:
dns_config.#
doesn't cause issues (it seems necessary fordns_config.0.additive_vpc_scope_dns_domain
to existadditive_vpc_scope_dns_domain
#11744 to ForceNew when domain changes is exactly the behavior we want and copy it overRelease Note Template for Downstream PRs (will be copied)
See Write release notes for guidance.